home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
netcoop.zip
/
NET-COOP.ASC
Wrap
Text File
|
1989-11-08
|
14KB
|
269 lines
The GT "Cooperative" Network
============================
The key word here is "Cooperative", as there are no rules or
laws, and the GT System Operators cooperate with each other to
move the network mail and echo conferences. This is an informal
organization, so this is to describe the basic steps for sysops
requesting and maintaining netmail and echomail functions. These
steps involve requesting Net/Node numbers with corresponding CRCs
and requesting Echo Conference numbers with corresponding CRCs. A
"Cooperative" being supportive in nature and in consideration for
the time demands to operate a Bulletin Board Network, have
selected a small group of GT Sysops to represent them in matters
concerning the operation of the GT Cooperative Network.
The ONLY Absolute Requirement to be a GT Bulletin Board
System Operator is that the user MUST be using his own registered
copy of the GT Power program.
** The Cooperation is made up of four basic parts. **
Briefly these parts are:
1. The first part is the foundation of the network, the GT Power
Sysops that are operating Bulletin Board Systems.
2. The second part is an appointed GT Sysop which has agreed to
distribute the CRC's necessary to operate the netmail
programs that move the mail, as well as distribute a current
list (NodeList) of persons/boards operating the netmail
programs.
3. The third part is an appointed sysop which has agreed to
distribute the CRCs necessary to "Sponsor" echoed
conference(s) on the network, as well as distribute a current
list (EchoList) of persons/boards sponsoring conferences.
4. The fourth part is a small group of selected sysops,
appointed by the majority of GT Sysops to represent them.
** Further Explained: **
I
The GT Power Sysops on this cooperative network are those
individuals that operate GT Bulletin Board Systems using GT Power
Software that they have registered with its producer, P & M
Software Company and received the necessary CRC for the program's
operation.
II.
They have also contacted the appointed GT Sysop that assigns
Netmail CRCs and had their board listed as a GT Power BBS for a
period of time to demonstrate their ability to operate the program
successfully. They have also demonstrated their ability to
operate the netmail programs successfully by sending a message to
the netmail sysop that issued their CRC. This being completed
they will then be added to the "NodeList" which the netmail sysop
will maintain and distribute on a regularly scheduled basis.
III.
They may have, if they wished to sponsor an Echo conference,
also contacted the appointed GT Sysop that assigns echomail CRCs
and requested that a conference on a particular topic be assigned
a CRC for their board. They have included in their request for an
Echo conference CRC, the description of their requested Echo
conference. They have agreed to maintain the conferences they
sponsor so that there are a minimum number of duplicate messages
distributed. They have agreed to be responsible for the content
of their echo conference and its method of distribution. They
have included in the echo's description, the hours that it will be
available for mail pickup from the sponsor's board. They have
also included the area of expected distribution for such requested
Echo conference(s).
IV.
They have agreed to abide by the decisions of the small group
of selected GT Sysops that represent them concerning their
participation on the network. This small group shall be selected
by GT Sysop members of the network. The method of their selection
will be under the control of one appointed GT Sysop (which is not
part of the selected group) that has been unanimously selected by
this small group of GT Sysops. This selected group shall be
decided on an annual basis for a term of one year with no sysop
being selected for more than four consecutive years.
They have agreed to the replacement of the CRCs for the
netmail and echomail on an annual basis after the small group has
provided their appointed netmail sysop and echomail sysop with the
new seeds for the CRC generators they are custodians of. The size
and number of GT Sysops in the small group shall be decided on an
annual basis at the same time that representatives are selected.
This newly decided number will be the basis for the following
years selection.
------------------------------------------------------------------
** Appointed Netmail CRC Sysop's Guidelines **
GT Cooperative Network Participation
1. Responsibility and Accountability are the sysop's keys to the
GT Cooperative Network participation, both initially as well
as on a continuing basis.
a. Registered GT Systems only.
b. Maintain a verifiable GT hosted system with a degree of
competence and personal satisfaction, keeping netmail
related files current.
c. Out-of-net calls are only by Prior Arrangement and
utilized when mail or echo pickups are unavailable
within local net.
2. Non-PCPursuitable systems need to initiate any long distance
calls for mail pickup. Local and Regional Sources are under
no obligation to incur long distance costs of delivery.
3. Broadcast messages are for the following uses only...
a. routing of network documents to Local or Regional Hubs,
who will in turn re-distribute according to local
schedule and overall need.
b. as economic consideration for Non-PCPursuitable nodes
and out-of-country nodes; foreign broadcast messages
will not be forwarded without prior agreement!
4. Netmail Files such as the "NodeList.BBS" are primarily
intended for netmail purposes. Please consult the GTBBS file
or similar listing for hours of operation other than during
netmail. A NodeList should not be available to the general
public.
The NodeList.BBS, as revised, will be distributed via netmail
and sent to all local hubs for further distribution within
their nets. Local hubs with no other nodes within their nets
will get distribution from their regional hubs.
------------------------------------------------------------------
** Appointed Echomail CRC Sysop's Guidelines **
GT Cooperative Network Participation
1. Responsibility and Accountability are the sysop's keys to the
GT Cooperative Network participation, both initially as well as on
a continuing basis.
a. Registered GT Systems only.
b. Maintain established scheduled echomail pickup hours.
c. Out-of-net calls are ONLY by Prior Arrangement and
utilized when echo pickups or distributions are not
available within the local nets.
d. Minimize duplication of messages in echo conferences.
e. Adhere to the published subject or topic chosen.
2. Non-PCPursuitable systems need to initiate any long distance
calls for echo pickup unless prior arrangement is made
through other incoming calls. Local and Regional Sources are
under no obligation to incur long distance costs for pickup
or delivery of echo conferences.
3. Echomail Files such as the "EchoList.BBS" are primarily
intended for Echomail purposes. Please consult the GTBBS
file or similar listing for hours of operation other than
during netmail. A EchoList should not be available to the
general public.
The EchoList.BBS, as revised, will be distributed via netmail
and sent to all local hubs for further distribution within
their nets. Local hubs with no other nodes within their nets
will get distribution from their regional hubs.
------------------------------------------------------------------
** Netmail CRC Request Procedures **
Please do not apply for a CRC and Net/Node number until you
have been running a GT hosted system with a degree of competence
and to your satisfaction. Your system should be listed in the
"GTBBS" list prior to your network request. It is understood that
participation in the GT Cooperative Network is reciprocal. The
board's telephone number is published in the nodelist and should
be accessible by any other system during the established netmail
hour(s).
If an existing Net is serving your dialing area, your CRC and
Net/Node number will be forwarded via that local hub's sysop for
coordination and testing.
The NodeList entry for a new network participant will show
"*PENDING*" until a netmail message is sent to the Netmail CRC
GT Sysop indicating successful network implementation. The local
net/hub's GT Sysop will also verify and recommend that the PENDING
be removed.
------------------------------------------------------------------
** Echomail CRC Request Procedures **
The requesting sysop MUST possess a valid Net/Node number and
CRC in the GT Cooperative Network as reflected in the current
NodeList.
The subject or topic of requested conference(s) MUST not
threaten the reputation or liability of GT Sysops in the network.
The requesting GT Sysop MUST furnish the time that their
board will have the sponsored echo(s) available for pickup. Also,
if their are any restrictions concerning its distribution, viewing
or that its bags are garbled.
All requests MUST include a description of the subject matter
or purpose of the echo conference(s). i.e. a discussion of modem
protocols, or regional sysops special interest conference...
------------------------------------------------------------------
** What Name for a Network? **
The name used in the example of a GT Power network above was
"GT Cooperative Network" because it is based on the GT Power Sysop
Bulletin Boards "Cooperation" to function. By nature, in business
and social relations, power is found in its "Cooperation". So,
why not call this suggested network "The GT Power Network"?
------------------------------------------------------------------
** Voting Method? **
This topic was deliberately not covered here. For any group
to be successful it must have effective and responsive leadership,
so the first objective of the suggested small group of
representatives should be to present how voting will take place.
------------------------------------------------------------------
** Personal Comments... **
The attached description was based on the collection of ideas
mentioned or suggested by others in the GT Network which thought
the growth and harmony were vital to a networks future and a few
ideas of my own. This description is presented as a suggestion.
Anyone that may have additional ideas is encouraged to make them.
Its these ideas and their communication that will make the future
expectations of those involved in any group activity successful.
If these suggested descriptions for the proposed network's
growth are acceptable, then messages to that affect should be sent
and suggested sysops to be a part of the selected small group to
represent the GT Power Sysops should be included.
Personally, nine (9) GT Power Sysops sounds like a good odd
number to start with for such a small group. Sounds like the nine
old judges for the Supreme Court. Also, being an odd number it
would make coming to a decision much easier.